home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
btrieve
/
xtr401.exe
/
BUGS.401
< prev
next >
Wrap
Text File
|
1991-09-05
|
38KB
|
990 lines
XTRIEVE & REPORT OPTION
*1. Receive error 227 when defining conditional field or restriction on view.
This will only happen when you define a condition which involves two
fields, not a field and a constant.
(e.g. field_a = field_b, field_c > field_d, etc.)
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
*2. The option "File" always appears at the bottom of the Main Menu, but
when you select it, XTRIEVE asks for the command to RUN.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
3. Some field default values are not being displayed as defaults when adding
data for a field which is in the view (EDIT/ADD).
DOS : Patch (Xtrieve.exe)
OS/2: Not patchable, Source fix next release
4. From the Main Menu, select DICTIONARY, ATTRIBUTES, then select a
file name, then a field name, then DEFAULT (which allows you to specify
a default field value). If you type in a value, the press ENTER (or just
press ENTER), a garbaged window is displayed on the screen.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
5. This patch is to force Xtrieve to unload XQLP and BTRIEVE, provided they
are loaded when Xtrieve terminates.
DOS : Patch (Xtrieve.exe) *** OPTIONAL ***
6. This patch is to stop Xtrieve from waiting for a key when returning from
a "Run" command.
DOS : Patch (Xtrieve.exe) *** OPTIONAL ***
*7. If you translate a view to SDF (or DIF), and your view contains
non-numeric fields (STRING,LSTRING,ZSTRING), and a value for the
non-numeric field is the null string (""), then if you try to translate
that data value back in to XTRIEVE in a numeric field, your machine may
lock up (or in OS/2 you may get a protection violation).
NOTE: The patch for this problem will keep Xtrieve from locking up (or
getting a protection violation) , but the value inserted into your file
for that field is unpredictable.
AS OF 4PM - 09/16/88 The patch has been enhanced to make sure the value
inserted is 0.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
*8. If you try to reorganize (and replace) a file which is used in an active
view, you will get a message that the file must be released from the
view (which is correct), and then the following message:
"Drive not ready, make sure disk is in drive and drive door is closed"
This is an incorrect message. If you procede much further in XTRIEVE,
you will receive many occurences of the above message. See #10 for an
explanation of this message.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
9. If you receive an error when adding, or modifying, records you are placed
at the top record, which has also been reinitialized, instead of at the
record which caused the error.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
*10. When XTRIEVE runs out of internal buffer space, it displays the error
"Drive not ready, make sure disk is in drive and drive door is closed"
This message is not the correct message, it should be
"No buffer space available"
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
11. OS/2: define file to dictionary gets the message
"Drive not ready, make sure disk is in drive and drive door is closed"
after specifying the disk file name and descriptive name.
EITHER: If editing a field value for a data record, you may get the
same message.
If you get this error in the above instances, your machine will
lock up (DOS) or get a protection violation (OS/2)
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
12. REPORT OPTION - fix is to XTRIEVE.EXE & XREPORT.OVL
"Error -1" when recalling a report in the report option (In OS/2, the
patch is for XTRIEVE.EXE. In DOS, the patch is in two parts: one for
XTRIEVE.EXE, one for XREPORT.OVL).
DOS : Patch (Xtrieve.exe & XReport.ovl)
OS/2: Patch (Xtrieve.exe)
*13. "Unable to add field to view, status = 207" after selecting a field to
add to the current view.
Workaround : ESCAPE from the ADD menu, then select ADD and select the
same field from the menu and the field should be added OK.
DOS : Patch (Xtrieve.exe), Workaround
OS/2: Patch (Xtrieve.exe), Workaround
*14. The cursor is not visible in the entry window immediately after Xtrieve
encounters a PROMPT key when replaying a command file.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
15. REPORT OPTION
ESCAPE from last report line prompt (when adding or modifying page
footings) drops you into the report instead of backing out (It acts
just like if you had pressed ENTER instead of ESCAPE).
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
16. REPORT OPTION
A report item which is positioned as the first item on a line, with an
absolute line position and a relative column position will appear
correct when SHOWing the report, but when printing, the item will appear
on the form too many characters to the right, any other items on that
line which are column relative to that item will also be off by the same
amount.
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
17. Translate to SDF or DIF places invalid characters in translate file when
the display mask for the field is from the dictionary and not defined
by the user specifically for the view. These characters may
be: commas, dashes, dollar signs, etc.
WORKAROUND: Modify the display mask so that it is just slightly
different from the dictionary mask.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
*18. Xtrieve Tutorial lesson1 gets error 204 adding field to view. Lesson2
gets error joining file to view.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
*19. Xtrieve toggles incorrect menu selections when security is enabled.
(eg. the configure option on the main menu is not toggled, but the
dictionary switch is toggled instead)
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
20. If a user has been granted only read access at the file level, and that
user attempts to "edit" some records in the file, the machine hangs up.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
21. If a user is granted write access at the file level, but only read
access for some fields in the file, and that user attempts to "edit"
fields for which the user only has read access, the machine hangs up.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
22. If all fields in a view are changed to TITLE fields, then Xtrieve does
not allow you to delete, clear, or show any of the fields in your view.
WORKAROUND: In order to allow any of these operations, you must first
add an additional non-title field to the view, and then
select the operation you want to perform.
DOS : Patch (Xtrieve.exe), Workaround
OS/2: Patch (Xtrieve.exe), Workaround
23. Xtrieve does not remember the security access rights that a user has
at the file level. Every time you try to specify the file level rights
for a user, it appears as though the user has no access for any files.
If you escape without resetting the user's access rights, the user will
loose access to all files.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
24. Xtrieve security allows user names which contain spaces, but after
defining the user, the master user is unable to modify, delete, or show
the access rights for the user.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
25. REPORT OPTION
May not be able to move an item from the middle of the report to the end
of the report (or from the middle of the group field list to the end of
the group field list, or likewise with summaries).
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
26. REPORT OPTION
If a user-defined summary runs into a case where you divide by 0 to get
the result, the system drops you back to the DOS prompt with the message
"MATH OVERFLOW".
DOS : Patch (XReport.ovl)
OS/2: Not patchable, Source fix next release
27. REPORT OPTION
If you print a layout definition, and then try to print the data
according to the layout, you may get the error "Drive not ready..."
which is an "Out of buffer space" message.
WORKARAOUND: To print the data for the report, ESCAPE to the MAIN menu,
then select REPORT/PRINT and you will be able to print the report.
DOS : Not patchable, Source fix next release, Workaround
OS/2: Not patchable, Source fix next release, Workaround
28. REPORT OPTION
Printing data from a report layout to 123 worksheet file may cause
system to hang. This happens most often when the report layout contains
summary items.
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
29. If you try to reorganize a file definition, then if you have loaded
XTRIEVE with very large parameters (W:4096 will do it), then you may get
"Drive not ready..." after specifying descriptive and disk file names for
the file. You are then left in the reorganization process, but you are
unable to do anything. If you have installed patch #11, Xtrieve will
still give you an error message (same unless #10 installed), then drop
you back to the DICTIONARY menu, but it does not close all the necessary
menus, so the menus appear abnormally.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
30. Translate to SDF from a DATE, TIME, or LOGICAL field value is OK, but
when you translate it back in (from SDF), the values are not what they
were before being translated (or after translated - in SDF file).
NOTE: 10/24/88 - This problem was reported today, so a change has been
made to patch #7 to fix this problem. If you have either problem #7 or
this problem, install patch #7.
DOS : Changes to patch #7 on 10/24/88
OS/2: Changes to patch #7 on 10/24/88
31. REPORT OPTION
If you receive an error while modifying a field in a report, and then
try to modify any other field (not a constant, only string fields), the
screen may flicker to the layout and then back to the menu to make you
select another field (It should let you modify the field).
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
32. The "not like" operator acts the same as the "contains" operator
when building a conditional statement for a restriction or a conditional
field.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
33. If your dictionary contains > 255 files, then you may get the error
"dictionary is empty" when defining a view, or manipulating a dictionary
file.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
34. If the number of fields in all the files in your view add up to > 255
then the last file which could fit on the menu will not have any fields
for that file in the menu.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
35. If you try to specify a default value for a LOGICAL field, your machine
will probably lock up when defining the default value.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
36. When you create a command file which chains another command file, by the
FCHAIN command, or creates a menu of command files to replay, FMENU, then
the command file, or list of command files, to replay will not be stored
in the command file correctly, thereby generating an error when it is
replayed.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
37. If you translate data from DIF to a TIME field, the value will be
translated as a value of 0.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
38. Xtrieve does not terminate the name of the help file when calling
Btrieve to open the Xtrieve help file. May cause Netware SQL to
get a GPI.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
39. REPORT OPTION
Date values printed to a 123 worksheet file (with the Report Option) are
1 day less than Lotus expects.
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
40. Integer values translated to SDF files contain a terminating '.' before
the comma separator (or end of line). This conflicts with previous
versions, and is not necessary.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
41. You may receive an error 299 when you select one of the first few
fields (or the first <file>.* entry) from the field menu for a view.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
42. REPORT OPTION
If you change your default print dimensions in the configure menu to
a large enough value (200 width, 90 length), the Report Option allows
you to define a report with the dimensions, but when you select
DIMENSIONS from the Report menu, and accept the default width and
length values, you will receive an error that the page/form dimensions
are invalid.
DOS : Patch (XReport.ovl)
OS/2: Patch (Xtrieve.exe)
43. If you give a user WRITE access at the FILE level, then check the
field level rights for that user on the same file, the users rights
for that file will be incorrectly changed to read only access.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
44. Get protection violation when you try to modify the second operand of
a restriction in OS/2. In DOS, you may get an error that the field
in the restriction is invalid (bad join index for example).
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
45. When setting print attributes, if you place a separator (, SPACE, etc.)
between hex values for a starting or stop sequence, and you specify an
8 character sequence, Xtrieve disregards the last character (or the
last 2 byte hex number).
WORKAROUND : Place all the hex numbers in the sequence next to each
other with no intervening delimiters.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
46. If you perform a MODIFY/REMOVE ALL on a view which has a user-defined
sort, XTRIEVE will go into an infinite loop when you answer YES to
"Are You Sure?". The reject count will grow continuously.
The patch will keep Xtrieve from locking up, but will not give you an
error message. The error message will be inserted in next release.
WORKAROUND : Press Ctrl-BREAK when Xtrieve goes into the loop.
DOS : Patch (Xtrieve.exe), Workaround
OS/2: Patch (Xtrieve.exe), Workaround
47. If you define a decimal field with >= 10 decimal positions, then when
you try to SHOW/REORGANIZE that file, the decimal places will appear
with a value 10 less than what it is defined as.
DOS : Patch (Xtrieve.exe)
OS/2: Patch (Xtrieve.exe)
48. REPORT OPTION
If you have a report which has > 1 form per page, and the forms do
not line up properly on each form, the report option may lock up at
the time when a page is printed.
DOS : Patch (XReport.ovl)
OS/2: (???)
49. REPORT OPTION
If you have 2 or more groups, and the first group is the first item on
the report, no named summaries in any nested group will appear in the
menu of fields for a user-defined summary for the first group.
DOS : Patch (XReport.ovl)
OS/2: (???)
50. If a constant used in a conditional expression for a user-defined field
contains spaces, then those spaces will be replaced with the caret ('^')
character when displayed.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
51. REPORT OPTION
The report option does not allow you to specify a name for a group
field. The title for the menu for naming the group fields will appear
incorrectly, and nothing will happen when you select any group field
from the name menu.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
52. REPORT OPTION
If you try to modify the last heading on your report, and you have
non-headings in your report, and you place the position cursor after the
last heading, then when you press enter for the column position, your
machine locks up.
The same thing also happens if you try to modify the last non-footing
on the report, and you have footings in the report, and you position the
cursor after the last non-footing.
DOS : Patch (XReport.ovl)
OS/2: (???)
53. XTRIEVE is unable to recall a stored view which requires an owner name.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
54. XTRIEVE incorrectly allows a user name which is all blanks (in essence
this is allowing no user name).
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
55. REPORT OPTION
System reboots when trying to delete a summary group field
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
56. A stored view which does not have a heading for some field will not
show any fields beyond this field whenever the view is RECALLED.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
57. Xtrieve opens a file which requires an owner name for write access, but
no owner name for read access. But Xtrieve does not use an owner name
so the file is opened for read-only. Xtrieve should open the file using
the first owner name specified.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
58. The heading line for the definition printing of dictionary files, views,
and layouts contains the words 'Xtrieve 4.00'. They should be
'Xtrieve 4.01'.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
59. If you are using Netware SQL with Xtrieve, and you attempt to change
your View directory to a local drive, you will get the error
"Release all views containing X$View before changing view directory"
You should receive some error, but this message is not appropriate to
the problem encountered.
WORKAROUND: Your view directory must be accessible from the server
which contains your dictionary files. A local drive can
not be accessed from any server.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
60. If you remove a supplemental index, Xtrieve does not give the "Yes/No"
menu so that you can change your mind.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
61. Default values for date fields are not being displayed for first record
during EDIT/ADD. Second and later records do show default value.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
62. If you load Xtrieve with /w:8040 or higher and /v:8 (other large
parameters also), and you define a view, then RUN a DOS command with
the RUN command. When you return to Xtrieve, you will receive an error
202 the next time Xtrieve makes a call to XQLP (Next BROWSE, or attempt
to STORE, or add fields, etc.). Any parameters large enough to require
that Xtrieve reserve > 64K of memory for retaining view information will
cause this error.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
63. Meaningless error message displayed if you try to define a NOTE
(or LVAR) field at any position except the last when defining a
file (DICTIONARY/DEFINE).
DOS : Not patchable, Additional message in next release
OS/2: Not patchable, Additional message in next release
64. XTRIEVE (DOS ONLY)
After installing patch #46, you will probably not be able to perform a
REMOVE ALL. This function will remove at 2 most records, and then quit,
no matter how many records should be removed. (If you only wanted to
remove 2 or less records, it works correctly.)
DOS : Patch #46 modified (Xtrieve.exe)
OS/2: Does not apply
65. When you EDIT/REMOVE records, and then select continue, the entire
window of records disappears except for the highlighted record.
WORKAROUND: Press the "Repaint" function key (Defaults to F10), or
else as you move the highlight bar up and down, the records
will appear again.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
66. If you set a condition for a user-defined field (or a view restriction),
and both the first and second operands in the condition are user-defined
fields, and the comparison is (<, >, !=, or "does not contain"), and the
first operand is displayed to the left of the second operand when
browsing your view (has a lower display offset), then the condition may
not select correct records.
WORKAROUND: Reposition your user-defined fields so that the first
operand in the condition has a higher display offset than
the second operand when both operands are user-defined
fields.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
67. When fields are changed to title fields, you may be able to browse more
records per screen than when the fields were not title fields.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
68. If two or more fields are changed to title fields, in a different order
than when they were non-title fields, without ESCAPEing from the
FIELD/TITLE menu, all subsequent fields changed to title fields until
you escape from the menu may not display the correct data when reading
data.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
69. Print to CON in VIEW/SUMMARY/PRINT gives error "Error writing output"
after displaying the results and you have pressed a key.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
70. Xtrieve incorrectly allows you to define a STRING, LSTRING, or ZSTRING
field of size 256 when defining a field to the dictionary. It also
allows a MONEY field of size 1, which is too small.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
71. If you define a printer attribute (in CONFIGURE/PRINT/ATTRIBUTES) which
has 8 characters in the stop sequence, the first character of the name
for the next attribute will be overwritten.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
72. If you have already installed patch #45, and then define an empty
sequence for some attribute, your machine will hang, or display the
first non-blank attribute sequence.
DOS : Patch #45 modified
OS/2: (???)
73. If you store a view which had fields that used the default or dictionary
mask, then before you recall that view, you define a dictionary mask for
the field, the view will not use the new dictionary mask.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
74. If you define a very large restriction (> 1000 bytes), when you complete
the definition, the restriction may be discarded.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
75. Xtrieve does not allow you to define a report layout which is 10,000 or
greater in width.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
76. If CTRL-BREAK is pressed when printing a definition, Xtrieve will abort
when it has finished printing the definition. It should stop printing
the definition when you press CTRL-BREAK.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
77. If you receive an error continuing a restriction, the existing
restricition is removed from the view.
DOS : Not patchable, Source fix next release
OS/2: Not patchable, Source fix next release
78. If you received patch #67 before 8/7/89, when you show a dictionary
definition, your machine may lock up. You must reinstall patch #67
to eliminate this problem.
DOS : Patch #67 modified (Xtrieve.exe)
OS/2: (???)
79. If Xtrieve is unable to display the definition for a user-defined field,
then further operation confuses the menu display to an unreadable
state.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
80. If user restricts a string field using the like operator, and includes
another condition after the first, then if any field or constant after
the condition with the like operator contains an underscore character,
that character will be changed to a question mark.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
81. Any view which contains title fields does not define user-defined
sorts correctly.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
82. Xtrieve hangs when using /k: parameter
DOS : Patch (Xtrieve.exe)
OS/2: (???)
83. Modification to patch #70. Also need to modify error message in
Xtrieve.msg to indicate that the maximum field length is 255 bytes.
In xtrieve.msg, message #400:
"Lstring and Zstring fields must be > 1 and <= 255 bytes"
In xtrieve.msg, message #404:
"String fields may be from 1 to 255 inclusive"
84. Xtrieve stores the unencrypted password in the configuration file when
security is installed.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
85. Xtrieve does not use the dictionary mask for the constant value when
restricting where a field is compared to a constant value.
DOS : Not patchable, Source fix next release.
OS/2: Not patchable, Source fix next release.
86. Xtrieve does not scroll the edit screen back to the first field in
the view unless that field is editable.
DOS : Not patchable, Source fix next release.
OS/2: Not patchable, Source fix next release.
87. REPORT OPTION
Printing an integer field with a decimal mask (e.g. -ZZZ.99) does not
use the scaling factor when printing to a 123 worksheet file.
DOS : Not patchable, Source fix next release.
OS/2: Not patchable, Source fix next release.
88. REPORT OPTION
Printing a report with headers to a 123 worksheet file places the first
heading in cell b1 (first row, second column) of the worksheet. This
only happens if the header is placed on absolute line 1, or on relative
line +0.
DOS : Patch (XReport.ovl)
OS/2: (???)
89. If you deny write access to a user at the field level, and then try to
allow access for the field just denied (must escaped from menu and then
come back in), Xtrieve does not allow you to grant write access to that
field.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
90. OS/2
Xtrieve hangs after user enters constant value when defining
restriction.
DOS : Does not apply
OS/2: Modification to patch #39 on 04/24/90
91. EDIT/ADD always uses the false value as the default for a logical
field, no matter what the default value was set to in the dictionary
attributes file.
DOS : Not patchable, Source fix next release.
OS/2: Not patchable, Source fix next release.
92. If you try to recall a view which has more fields than the value of
the /f parameter at load time, Xtrieve may hang, or act unpredictably
afterwards.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
93. If you set the SECURITY option to YES, but do not save the
configuration file. When you get back to the main menu, the CONFIGURE
option is not longer visible. If you select security and add a user,
you will get this error:
"ASCII strings containing digits, leading zero digits (1 to 15 bytes)"
which is meaningless here. This patch changes the error message to:
"Internal error 203, note this error and contact technical support"
You must save the configuration file before security is installed
on the current dictionary.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
94. When security is installed on a dictionary, you may get garbage for some
of the file names in a DICTIONARY SHOW/REORGANIZE/INDEX menu (or other
menus which prompt for a file name).
DOS : Patch (Xtrieve.exe)
OS/2: (???)
95. Create a view which has user-defined fields, and delete one or more of
them. If the user-defined you delete are not the last ones defined,
then if you store and recall the view, you will get an error 345 when
you try to define a user-defined field for the view.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
NOTE: After installing this patch, you will get an error 345 if you
try to define more than one user-defined field with the same first 19
characters.
*************************** ATTENTION ********************************
This patch was modified on 8/16/90, and redistributed with the changes
on 8/29/90. Original patch could cause an error 345 when a second
user-defined field was added to the view.
96. REPORT OPTION
The heading for the GROUP/NAME menu is being displayed as MODIFY instead
of NAME.
DOS : Patch (XReport.ovl)
OS/2: (???)
97. When you use the XTRPINDX variable, Xtrieve prepends the specified path
to the DOS filename in the dictionary, in addition to creating it where
you specify. If you specify the directory to create the file with a
complete path, the file will be created, but if the directory is
relative to the current path, the file may not be created.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
98. If you perform a Modify All (or Remove All), Xtrieve always attempts
to start a transaction on the view, regardless of the setting of the
Lock flag from the configuration file.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
99. When an INTEGER with a mask which has decimal places is translated out
to SDF/DIF files, the value goes out scaled according to the mask.
But, when translated back in from the SDF/DIF file, the value is not
unscaled before inserting into the data file. So, a value of 345 with
a mask of ZZZ.99 will be translated out as 3.45, but when translated
back in will have a value of 3 (regardless of the mask).
NOTE: Xtrieve should use the mask also when translating in, so the
value should be translated in as 345 (provided the mask is still
ZZZ.99. If the mask was ZZZ.9, then the value should be translated in
as 34).
DOS : Not patchable, Source fix next release.
OS/2: Not patchable, Source fix next release.
100. Receive a status 11 when trying to create a dictionary.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
101. Receive "Dictionary is empty" message when VIEW.DDF contains more than
254 view definitions, and you try to recall, or remove, a view. Store
works OK, though.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
102. When you install security on you dictionary and immediately attempt
to add your users to the dictionary, you get an error message:
"Internal error 203, note this error and contact technical support"
DOS : Patch (Xtrieve.exe)
OS/2: (???)
103. When joining two files, the JOIN option in XTRIEVE does not properly
display the file names at the bottom of the file selection listing
(characters may be missing from the beginning of the file name or the
file names may appear corrupted). This was only a problem if security was
installed.
DOS : Patch (Xtrieve.exe)
OS/2: (???)
*******************************************************************************
XTRIEVE UTILITIES
MAKE_XTA
DOS : New MAKE_XTA.exe on Compuserve (FIXED in 4.01a)
OS/2: New MAKE_XTA.exe on Compuserve
1. MAKE_XTA may not place the mask for a field in a layout when generating
the XTA file for the layout. Patch available to Report Option to fix
this (In OS/2 version, the patch is for XTRIEVE.EXE, In DOS, the patch is
for XREPORT.OVL).
2. User-defined summaries are not placed correctly in XTA file. The text,
mask, and position are placed in the XTA file twice.
3. System may hang while "Extracting supplemental indexes ..." using the
/F option of MAKE_XTA.
4. MAKE_XTA does not allow you to specify a path name for any parameter,
but accepts 2 backslashes and converts them to a single backslash.
***** This is patchable. *****
NOTE: THE USE OF 2 BACKSLASHES WILL NOT BE SUPPORTED IN THE FUTURE.
*******************************************************************************
XCFP
DOS : New XCFP.exe on Compuserve (FIXED in 4.01a)
OS/2: New XCFP.exe on Compuserve
1. Not recognizing various commands when converting from XTA to XTC, and XTC
to XTA not converting some selections to "DOT" commands.
2. XCFP may create a file without .XTA or .XTC extension if you specify
an output file without an extension.
*********XCFP************ REPORTED AFTER 4.01a RELEASE *********XCFP***********
WILL NOT BE FIXED UNTIL NEXT RELEASE
3. XCFP does not report error if a command is not delimited by any valid
delimiter in the XTA file. It just stops processing the XTA file, not
putting the command which was delimited, or any commands after that one
in the XTC file.
4. If you have a constant value which ends in the '+' character, then if a
function key, or cursor movement key directly follows the constant in
the .XTC file and you convert the file to .XTA format, the key after the
constant value will not be included in the .XTA file.
5. If you have a large constant value in your command file
(> ~ 80 characters) then your machine will probably lock up when
converting the .XTC file to a .XTA file.
*******************************************************************************
UPGRADE
DOS : New UPGRADE.exe on Compuserve (FIXED in 4.01a)
OS/2: New UPGRADE.exe on Compuserve
1. FYI:
If you upgrade your command files, any command file which joins a file
to the view will not convert correctly. After upgrading, the index from
the secondary file used in the join must be modified in the command file.
2. When upgrading command files, if your command file selects all the fields
from a file (in a view) by selecting "<filename>.*", then the converted
file will have the period before the '*' removed. This will be fixed in
the next release, but you may modify the command file by reinserting the
period before the '*'.
3. Upgrading views may not store constants for expressions (USER_DEFINED
FIELDS or RESTRICTIONS) properly. You will be able to recall the view,
but the constants may not be correct. This is unpatchable, but you may
run MAKE_XTA on the new view, and change the constants in the .XTA file
created, and then recreate the view by running the command file in
XTRIEVE.
*******************************************************************************
XMENU
DOS : New XMENU.exe on Compuserve (FIXED in 4.01a)
OS/2: New XMENU.exe on Compuserve
1. XMENU does not allow menu items to be repositioned correctly.
*******************************************************************************
* means that this bug is new for version 4.01, if a bug does not have this
symbol beside it, then that problem will most likely show up in version
4.00 also.
*******************************************************************************
REPORT EXECUTIVE
*******************************************************************************
1. If you try to execute a report which has groups, and the innermost
group does not contain any fields or summaries, the resulting data
may not be correct.
DOS : Patch (Rptexec.exe)
OS/2: (???)
*******************************************************************************